Direct and Reverse FrameWorX Connection Overview

You can use two modes when connecting to another FrameWorX Server: direct or reverse connection. Direct connections are the most common.

In a direct connection, the FrameWorX instance that wants to read the data initiates the connection, as in a typical server-client relationship. In a reverse connection, the FrameWorX instance that provides the data initiates the connection, opening a tunnel for communication.

Consider the following points when deciding whether to use a direct or reverse connection:

• If your target server (the one you are connecting to) is behind a Network Address Translation (NAT) or a firewall:
  • If you can create an inbound rule to allow FrameWorX communication, use a direct connection. Learn more

  • If you cannot create an inbound rule, use a reverse connection. Learn more

    A typical use case for a reverse connection is when you have one GENESIS server running in the cloud and another one on-premises. The cloud server's FrameWorX needs to subscribe to data from the on-premises FrameWorX. Since the on-premises FrameWorX is hidden behind a NAT, you cannot connect to that server using a direct connection. You must use a reverse connection.

• In any other case, use a direct connection. Learn more